-
Notifications
You must be signed in to change notification settings - Fork 2.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
add kind e2e test job for alpha features #29599
add kind e2e test job for alpha features #29599
Conversation
/lgtm |
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: BenTheElder, jiahuif The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
@jiahuif: Updated the
In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
This PR creates a
pull-kubernetes-e2e-kind-alpha-features
that is optional and opted-in to ease development of alpha features.The criteria of alpha feature tests is the
[Alpha]
label. Usual skips like[Slow]
,[Disruptive]
are preserved. Other settings are copied frompull-kubernetes-e2e-kind
job.Previously, when developing an alpha feature, we borrow the
pull-kubernetes-e2e-gce-cos-alpha-features
job in./config/jobs/kubernetes/sig-cloud-provider/gcp/gcp-gce.yaml
(example: #26994) . However, adding new feature gate to the list and remove it back later every time a new alpha feature starts is suboptimal. The new job this PR creates formalize the list as "alpha features" and run it withkind
to speed things up.NOTE: usually beta graduation requires E2E tests to be in place, which is why E2E tests for alpha features are rare.